Hello,
I would like to buld a script in DXL that would disconnect idle users after a period of time. The reason is that users who are connected through terminal server and do not log off accordingly remain connected for a long period of time.
Thanks
sab_ny - Thu Apr 07 02:35:09 EDT 2011 |
|
Re: DXL Script question
Mathias Mamsch - Thu Apr 07 06:45:10 EDT 2011
This has been discussed before. Logging off (disconnecting their sessions) is doable (you can use the dbadmin tool for that provided you have access to the database server and the database password). The problem is to detect idle time. This is not reliably possible from the DOORS client. So if you have information from the terminal server about idle sessions, and you can get a User ID for that session, and you can map it to the corresponding DOORS user, and you have the mentioned access to the DB server you might be able to pull off a script, which will disconnect the DOORS session. However I would not recommend that since disconnecting a session always has the risk of data corruption and the user will loose all his changes. So the time might be better invested in informing / training the people to log off properly. Just my two cents, regards, Mathias
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
|
|
Re: DXL Script question
sab_ny - Thu Apr 07 06:52:33 EDT 2011
Yes, I know about the dbadmin tool, but doing it manually is such a bother...
|
|
Re: DXL Script question
llandale - Thu Apr 07 11:20:35 EDT 2011
If someone had implemented some DOORS mechanism for detecting long idle users and gracefully saving their work and closing DOORS on their client, that person would surely have bragged about ..err.. shared it on these forums and rightfully so; earning the gold star.
While Possible, it doesn't seem Realistic; where 'possible' means perhaps 10 folks in the world could do it if they really wanted to; in a reasonable amount of time.
I suspect such a solution would including bribing some old Telelogic programmer to determine how to ask the DOORS service who has been idle for how long; or perhaps its asking the DOORS client. <It has this information since DOORS has a rude abort timeout feature as a Database Option>. You could perhaps coordinate that with some DXL 'timer' running on the client, perhaps every 10 minutes, which figures out idle and gracefull saves and closes and exits.
|
|